Note: This updater works with any previous U.S. or UK version of Falcon 4.0. You do not need to update to version 1.04 first before using the version 1.06 updater. (A U.S. or UK version 1.05 never existed.)
This updater can only be used with the U.S. or UK version of Falcon 4.0. Do not use this updater for any other language version!
1. Download the file F4106US.EXE to your hard drive.
2. Double-click F4106US.EXE to start the update.
3. Click the "Next" button at the Welcome screen to start the update.
4. The updater will automatically update your copy of Falcon 4.0 to version 1.06.
If you have any problems updating to version 1.06, first make sure that you have the U.S. or UK version of Falcon 4.0. Right-click on the FALCON4.EXE file and select Properties from the pop-up menu. The File Version should read either "(US Version)" or "(UK Version)."
If you still cannot update your copy to version 1.06, we recommend that you uninstall Falcon 4.0 and then reinstall the game before running the updater.
After you update to version 1.06, the File Version for FALCON4.EXE should now read "1,0,6."
Version 1.06 Changes
The following serious problems have been fixed in version 1.06:
* The crash in version 1.04 on computers with Voodoo 2 cards and Terrain Detail set to the highest setting has been fixed.
* If you used the Software graphics option (instead of Glide or Direct3D), the game would crash if you exited the simulation while in the 2-D Cockpit.
* If you padlocked onto an aircraft just as it exploded, the game would crash.
* If you selected the "Inbound" radio command after declaring an emergency landing, the game would crash.
* In Tactical Engagement, if you placed a ground supply unit in the ocean, the game would crash.
* In Tactical Engagement, if you clicked the Saved tab and then the Edit button while online, the game would crash.
* If you dropped a lot of weapons, the game would sometimes crash.
* If you selected a mission, entered the countdown screen, returned to the user interface, selected a different mission, entered the simulation and then looked at the kneeboard, the game would crash.
* If you entered the simulation, the game would sometimes crash during the loading screen.
* If you cycled the GBUs, the game would sometimes crash (especially if you switched to an outside view and then returned to the cockpit).
* If you clicked the Comms button and then selected "Sign Off" from within Dogfight, Tactical Engagement or Campaign, the game would crash. (If you returned to the main menu and then chose "Sign Off," the game worked fine.)
* Pressing the Mark button on the ICP with Combat autopilot engaged would crash the game.
* The game is more stable now in the Campaign user interface.
The following game problems have been fixed in version 1.06:
* In Dogfight, changing your starting location on the map works correctly.
* In Dogfight, the USA plane labels no longer change color.
* In Campaign and Tactical Engagement, the Debriefings now correctly list the player in the appropriate flight (for example, escort vs. strike).
* In Campaign, the Squadron History window now has the correct information for missions and ratings.
* In Campaign, the scroll bar for the Campaign Saved list now works.
* In Tactical Engagement, the clock now works correctly (it will now go past Day 1).
* In Tactical Engagement, the flamer at high altitude.
* The FLCS (Flight Control System) can no longer pull Gs significantly above 9Gs. Therefore, the F-16 now behaves more realistically when pulling Gs near corner speed.
* The amount of fuel onboard no longer increases at high speeds at low altitude nor at idle at high altitude.
* AGM-88A HARMs now guide more accurately and thus are more effective.
* When you fire the last HARM, you can now change to other weapons, the cursors work and the game no longer occasionally crashes.
* You can now set your air-to-ground radar (GM, GMT or SEA) to standby (Ctrl-R) without the game crashing.
* You no longer have to double-click the Cursor Zero function in air-to-ground radar.
* The SMS no longer freezes if you try to ripple more bombs than you have on your F-16.
* Brakes no longer work if the landing gear collapses.
* Wingmen no longer add steerpoints to your HSD when they are low on fuel.
* AWACS now responds appropriately to the "Declare" radio command by calling out the target under your radar cursors.
* AWACS now correctly vectors players to threats and tankers.
* In Tactical Engagement, the kneeboard map now displays correct information, including steerpoints.
The following AI changes have been made in version 1.04:
* AI pilots no longer collide when changing formations.
* AI pilots now use air-to-ground weapons (including the recon camera) more effectively.
* AI pilots no longer return to base right after taking off.
* AI pilots behave more intelligently during dogfights, especially close-in dogfights.
* AI pilots do not "wiggle" their planes as much during dogfights.
* AI pilots use afterburner more appropriately (for example, they do not use afterburner as much during non-combat flight).
* AI pilots now land more reliably.
* Wingmen now respond appropriately when you tell them to attack.
* AI pilots now give their correct fuel states when you radio them.
* Ground traffic at airbases should no longer get cluttered (that is, fewer traffic jams on the taxiways).
The following radio changes have been made in version 1.04:
* Callsigns more accurately reflect the actual pilot now.
* ATC issues proper landing and takeoff clearances.
* AI pilots no longer repeat the same call as much.
* ATC now handles emergency landing requests more effectively.
The following multiplayer changes have been made in version 1.04:
* You will no longer enter the plane with the autopilot already engaged.
* In Dogfight and Campaign, you will now always see the ROE (Rules of Engagement) screen if your settings do not match the host's requirements.
* In Dogfight, you now correctly lose a single point if you eject or crash into the ground without being damaged.
* In a Dogfight game over the LAN, scoring should be correct.
* In Dogfight, all players should now see each other.
* Over a LAN, reentry issues within the Dogfight setup are fixed.
* In a Match Play game, the Sierra Hotel screen always comes up now when the match ends.
* In a Match Play game over a LAN, both players and AI aircraft now respawn correctly.
* In the Dogfight debriefing, ejecting without being damaged is now listed correctly in the Events list (rather than "Killed by debris").
* The Chat window now automatically scrolls.
* Chatting within the simulation (Shift-T) now works correctly. Remember, that if you want to talk to everyone (friendlies and enemies), you need to set your radio to the Broadcast channel (channel 6).
The following enhancements have been added to version 1.04:
* You can set your throttle's afterburner position to something other than the default. First, set your throttle to wherever you would like the afterburner detent to be. Then click the "Set AB" button at the Controllers setup screen. The AB position is marked with a green line on the Throttle readout.
* Some joysticks report to Windows that they have rudders even though none are connected. If you wish to disable any rudder input (regardless of whether you actually have rudder pedals or not), you can use the command line parameter of "-norudder." First, "Run" from the Start menu. Then, type "C:\MicroProse\Falcon4\falcon4.exe -norudder" in the Run dialog box.
* You can delete files from within the game by right-clicking on the filename in the Load dialog box and choosing "Delete." This means that you can now delete ACMI files from within Falcon 4.0.
The following graphics changes have been made in version 1.04:
* The special effects for sparks have been improved.
Version 1.03 Changes
The following crash problems have been fixed in version 1.03:
* Sometimes if you ejected in earlier versions, the game would crash.
* Pressing the MARK button on the ICP in earlier versions would crash the game.
* A period in the path name (such as "D:\Falcon4.0") caused the game to crash after the intro movie.
The following problems have been fixed in version 1.03:
* Some memory leaks in Campaign have been fixed.
* The mouse button sometimes stuck and remained in the "down" position (for zoom, time advance, etc.).
* Remapping keys caused radio command menus to not appear, etc.
* A space in the path name (such as "D:\Falcon 4") caused the command line parameters (such as
"-hires" and "-g#") to not work.
* The VVI (Vertical Velocity Indicator) was incorrect.
* Colonels (such as Klemmick and Bonanni) never died.
* Pilots Klemmick and Bonanni were duplicated (planes are now held with the label "Unassigned" until a pilot becomes available or until takeoff).
The following AI changes have been made in version 1.03:
* AI pilots now leave the fight when they run out of fuel.
* AI pilots now leave the fight when their planes are seriously damaged.
* AI pilots now wait longer on the taxiway for you to take off.
* AI pilots can now complete air-to-ground interdiction missions (such as Interdiction, BAI and SAD).
* AI wingmen now follow formation orders better.
* AI wingmen no longer collide with you.
* AI pilots are now better at avoiding the ground.
* AI pilots no longer radio the same message over and over again.
* AI pilots no longer drive on the ground to Steerpoint 1 (they now fly to Steerpoint 2).
* Aircraft no longer end up inside another (either on the ground or in the air).
The following radio changes have been made in version 1.03:
* ATC now gives the correct vectors for landing.
* ATC no longer repeats the same call.
* ATC now directs you correctly right vs. left.
* Radio calls now use the correct order, addressing the recipient first and then identifying the caller.
The following multiplayer changes have been made in version 1.03:
* Multiplayer connections are more stable.
* Scoring in multiplayer Dogfight games is now improved.
* The airspeed readout on radar in multiplayer Dogfight games is now correct.
* Aircraft are now eliminated from a multiplayer Dogfight game when that machine crashes.
* You can no longer give wingman commands in multiplayer Match Play when you are dead.
* Views are now restricted in multiplayer Match Play games once you die.
* The Event List in Dogfight no longer overwrites the text box.
The following graphics changes have been made in version 1.03:
* In Software graphics mode, the white line between the horizon and ground is now fixed.
* In Software graphics mode, the missile trails are no longer white at night.
* Napalm explosions are improved.
* Explosions now look better on the water.
* Colors on the life raft and/or parachute no longer flash.
The following enhancements have been added to version 1.03:
* The damage from bomb explosions (particularly napalm) are more realistic.
* You can press Alt-R in Dogfight games to toggle the score display.
* You can press Ctrl-Z, release the keys and then press "R" to display the frame rate counter.
FAQ (Frequently Asked Questions)
If you are having any problems with Falcon 4.0, please read this entire Readme file for more help. In addition, we recommend that you look at the Falcon 4.0 FAQ, available for downloading from our Web site as F4FAQ.DOC. The Falcon 4.0 FAQ contains helpful information on troubleshooting, graphics, gameplay, the simulation, etc.
Installation
Compact
The Compact installation option will install not only the game files, but also the object files onto your hard drive. Therefore, the Compact install will require approximately 150MB of hard drive space (not 140MB).
Custom
If you choose the Custom install option, be sure to mark the check box for "Program Files" or else you will not install the necessary game files and Falcon 4.0 will not run.
DirectX
After the installer copies all the game files to your hard drive, it will check your computer system to make sure that your version of DirectX is up to date. If you have DirectX version 5 or later, the installer will say "DirectX drivers on your system are current." If you have DirectX version 5, you can play Falcon 4.0 but you can also choose to upgrade to version 6 by clicking the box next to "DirectX 6." If you have a version of DirectX older than 5, you must upgrade since Falcon 4.0 requires at least DirectX version 5 in order to run. If you already have a compatible version of DirectX on your computer, you will not be prompted to update DirectX. If you ever need to reinstall DirectX, open the DirectX folder on the Falcon 4.0 CD-ROM and run SETUP.EXE.
Error Message
If you see the error message "-115" when you try to install Falcon 4.0, it may be caused by a program called NetZip. If NetZip is on your computer, it may prevent the Falcon 4.0 installer from copying a Zip file from the game CD-ROM to your hard drive. You need to remove NetZip to install the game.
Troubleshooting
Swap File
Because Falcon 4.0 is an extremely complex and realistic simulation, we recommend a swap file space on your hard drive of at least 200MB. Otherwise, the game may simply quit back to the Windows desktop when you try to run it. Even if you have the required amount of RAM (32MB) or more, you still need a large swap file. We recommend making sure that you have at least 200MB free on your hard drive and that you let Windows manage the swap file. Follow the instructions below:
1. Right-click on the icon for My Computer.
2. Select "Properties" from the pop-up menu.
3. Select the Performance tab.
4. Click the Virtual Memory button.
5. Select "Let Windows manage my virtual memory settings."
6. Click OK.
Using MPRTest
If Falcon 4.0 crashes with a black screen, please use the supplied utility MPRTest to check your video cards. Running MPRTEST.EXE displays a list of all available video cards drivers, devices and resolutions. Run "MPRtest.exe -help" for more information on how to use this utility to test your graphics capabilities. To run MPRTest, select "Run" from the Start menu and type "C:\MicroProse\Falcon4\MPRtest.exe" in the dialog box.
Task Switching
Do not press Alt-Tab to task switch while in the simulation. You can, however, press Alt-Tab while you are in the user interface.
Error Messages
If you see an error message about MSVCRT.DLL when you run Falcon 4.0, you need to copy this file to your Falcon 4.0 directory. Copy the file MSVCRT.DLL from the \Programs directory on your Falcon 4.0 CD-ROM to the Falcon 4.0 directory on your hard drive (usually C:\MicroProse\Falcon4).
If you see an error message "Invalid page fault," you may have the Glide driver for a Voodoo card without having a Voodoo card installed in your computer. For example, if you had a Voodoo card but then switched to a non-Voodoo card (such as a Riva TNT), Falcon 4.0 will not run if it detects a Glide driver on your computer. If Falcon 4.0 finds the GLIDE2X.DLL on your computer, it assumes that you have a Voodoo card. If you don't, then the game will not run and display the "Invalid page fault" error message. To solve this problem, rename the GR3DFX.MPR file from your Falcon 4.0 directory to OLDGR3DFX.MPDR. If you add a Voodoo card to your computer, we recommend reinstalling Falcon 4.0 again.
Enhancing Game Performance
If your computer system has less than 64MB RAM, we suggest setting both Object Density and Player Bubble to "1" in the Graphics setup screen.
If your computer system only meets the minimum specifications and you have chosen the Compact install (150MB), the game will take several minutes to load each mission. If you have enough hard drive space, we recommend installing the Typical version to reduce load times.
Freeing up Maximum Memory
To free up the maximum amount of memory in Windows, press Ctrl-Alt-Del at the Windows desktop. Close all programs listed in the dialog box except Explorer and Systray.
Hardware Compatibility
Mice With Scroll Wheels
If you have turned on the scroll wheel of your mouse, you may not be able to click on buttons, switches, etc. in the Falcon 4.0 cockpit. We recommend that you either turn off this feature from the control panel before running the game or use the standard Windows mouse driver.
PowerVR
If your computer system has a video card based on the PowerVR chipset, you must run Falcon 4.0 in Software mode, not Direct3D. Unfortunately, the PowerVR card does not have a frame buffer, which the program requires for Direct3D mode.
Color Corruption
If you are running Falcon 4.0 in Software graphics mode (not Direct3D or Glide), you may see incorrect colors, especially if you have an older 2-D video card. To correct this problem, use the ColorMode utility we have provided in the root Falcon 4.0 directory on your hard drive. To use this utility, select "Run" from the Start menu. Type "C:\MicroProse\Falcon4\ColorMode 555" in the Run dialog box. If that doesn't work to correct the problem, try typing "C:\MicroProse\Falcon4\ColorMode 565" in the Run dialog box. If you later change your video card, you can reset the game to automatically detect your graphics capability by running "ColorMode Auto."
3Dfx Voodoo 2
If you see an error message that says "Mutual exclusion prevents this," you need to update your Glide reference driver for the Voodoo 2 card to at least version 2.53 or later.
If you have installed version 2.54 of the Voodoo 2 reference drivers, your installed copy of DirectX must be version 6. Otherwise, the simulation graphics will not function correctly in Direct3D mode.
Video Cards
The following video cards require at least these driver versions:
3Dfx Voodoo 2 glide2x.dll 2.53 or higher www.3dfx.com
3Dfx Banshee glide2x.dll 2.53 or higher www.3dfx.com
3Dfx Voodoo glide2x.dll 2.46 or higher www.3dfx.com
We have included two utilities in the default Falcon 4.0 directory. F4INFO.EXE will give you information about Falcon 4.0, your video cards and DirectX. Run MPRTEST.EXE to display a list of all available video cards drivers, devices and resolutions. Run "MPRtest.exe -help" for more information on how to use this utility to test your graphics capabilities. To run either utility, select "Run" from the Start menu and type either "C:\MicroProse\Falcon4\F4info.exe" or "C:\MicroProse\Falcon4\MPRtest.exe" in the dialog box. We recommend running both of these utilities and printing out the information displayed onscreen before calling Customer Support with a problem.
Direct3D
The auto-detection for Direct3D graphics cards may not always work. In this case, your video card will appear available in the Graphics setup screen if you choose "Software" for the Video Driver but not if you choose "Direct3D." To force all Direct3D video cards to appear, you will have to edit your registry. Do not edit your registry unless you are an experienced computer user. You need to change "False" to "True" for HKEY_LOCAL_MACHINE\SOFTWARE\MicroProse\Falcon\4.0\MPR\MPRRAIID3DDevices.
Game Controllers
Remember that if you have a throttle on your joystick, you cannot press "+" and "-" on the keyboard to change your throttle. You must use the throttle on the joystick.
If you have rudder pedals, you cannot use "<" and ">" on the keyboard as rudder controls. You must use your rudder pedals.
CH Joysticks
To use the supplied CH CombatStick setup, be sure to download the Speedkeys utility from CH's Web site (www.chproducts.com). You need to use Speedkeys to create a directory where the supplied data file should go. All other CH joysticks should be set up using the Speedkeys utility.
Keyboard Flight Controls
If you do not have a joystick, you can fly your F-16 using the cursor keys on the keyboard. First, at the Controllers setup screen, click the Load button under Key Mapping. Next, select "Laptop" and click the Load button. This will remap the cursor keys to flight controls. Other keys are remapped as listed below. Remember that you cannot fly with the keyboard if you have a joystick attached.
Nose Down ß ICP A-G Button Ctrl-` (tilde key)
Nose Up Γ ICP MARK Button Ctrl-1
Bank Left ▀ ICP ENTER Button Ctrl-3
Bank Right α ICP STPT Button Ctrl-4
Move Radar Cursors Up Ctrl-ß ICP CRUS Button Ctrl-5
Move Radar Cursors Down Ctrl-Γ ICP DLNK Button Ctrl-6
Move Radar Cursors Left Ctrl-▀ ICP ILS Button Ctrl-7
Move Radar Cursors Right Ctrl-α ICP ALOW Button Ctrl-8
Radar Return to Search Ctrl-X Lock Target on Nose Ctrl-F2
Glance Backward Alt-[ Lock Next Target Ctrl-F3
Glance Forward Alt-]
Text Entry
Falcon 4.0 does not support using the numeric keypad or the CapsLock key for entering text in the user interface.
Higher Resolutions
If you want to access resolutions higher than 800 x 600 in the simulation, use the command line parameter of "-hires." First, select "Run" from the Start menu. Then, type "C:\MicroProse\Falcon4\falcon4.exe -hires" in the Run dialog box. If your computer system supports any higher graphics resolutions, the Resolution option at the Graphics setup screen will show the available choices: 1024 x 768, 1152 x 864, 1280 x 960 or 1600 x 1200. Please remember that which resolutions are available depends on your video card and its memory.
Unfortunately, the 2-D Cockpit view does not support graphics resolutions of 1024 x 768 and 1152 x 864. You will only see a HUD onscreen. To see the MFDs, switch to the HUD Only or Virtual Cockpit views. This means that at these higher resolutions, you will not be able to click on buttons, switches, etc. in the cockpit. (You will get a clickable cockpit if you choose 1280 x 960 or 1600 x 1200.)
Enhanced Graphics
If you have a high-end computer system, you can enhance your graphics. Use the command line parameter of "Falcon4.exe -g#" where "#" is either 2, 3 or 4. This parameter increases the maximum settings for Terrain Detail, Object Detail and Player Bubble in the Graphics setup screen. For example, if you run the game with "-g2," this will change the range of settings for these graphics options to 1 through 10 (vs. 1 through 5). Obviously, selecting a setting higher than 5 will take a large amount of RAM and decrease frame rate, but the game will run with more detailed graphics.
Gameplay
Mission Completion Criteria
Be sure to pay attention to what AWACS tells your flight. For example, AWACS may tell you to intercept enemy fighters while you are on CAP. You will need to successfully complete the intercept in order to successfully complete the entire mission.
To get complete success for a mission, you must not end the mission until you have completed your task and landed at your airbase. Otherwise, you will only get credit for a partial success even if you completed your task and end the mission in friendly airspace.
BAI (Battlefield Air Interdiction)
The purpose of BAI is to interdict enemy troops before they can reach the front line. To achieve success, you must destroy a reasonable number of enemy vehicles given the ordnance capacity of your aircraft.
Training Missions
If you are getting shot down in a training mission, try turning Invulnerability on in the Simulation setup screen. This should help you get through the entire training mission.
Logbook
The maximum size for the pilot picture is 96 x 96 pixels (not 144 x 110 as stated in the manual).
Landing
Once you request clearance to land, if you radio a command to your wingmen, they will not land. You must then tell them to "return to base" to get them to land.
When you are landing, the tower will only give you a heading if you are more than 5 degrees off the correct heading.
Views
If you would like to view the action in the simulation, set your autopilot to Combat mode, turn Invulnerability on and select Unlimited Fuel from the Simulation setup screen. Then, start the mission and select the Action Camera view by pressing Shift-tilde (Shift-~). The Action Camera will automatically switch viewpoints from one vehicle to the next, so you can get a feel for what is happening in the world without having to fly over it.
If you switched to the Action Camera view (Shift-tilde), you may need to toggle off the Look Closer view by pressing "L" after switching to a different view.
ACMI
If you record an ACMI tape during flight, it may take several minutes after you exit the simulation before you return to the user interface as the program processes the ACMI tape. You will see the Stand By screen during this time.
Remember that the ACMI file size that you set in the Simulation setup screen only determines the file size for each tape. Once each tape is full, the ACMI recorder will start a new tape (meaning a new file). Make sure that you have enough hard drive space to handle all the ACMI tapes you create during flight.
AWACS
If you radio "Declare" to AWACS, AWACS will try to determine whether the target you have is hostile or friendly. The position of the radar cursors is used to determine what target you want AWACS to declare. If you do not have a target under your radar cursors, then AWACS will declare the target you have locked up.
Tactical Engagement
The Edit button was removed from the Add Package window.
Wingmen
If your computer-controlled wingmen are getting too close to you, order them back into formation by radioing "Rejoin."
Multiplayer
We have had greater success when the person who hosts the game is not the person who sets up the game. That is, if Players B and C connect to Player A, we recommend that Player B or Player C actually sets up the multiplayer game (instead of Player A).
Do not press Shift-P for Freeze mode in multiplayer games.
Dogfight: When you die and then are "respawned," the plane starts with autopilot already engaged. You must press "A" to turn off the autopilot so you can fly the plane. When you set the Altitude for a multiplayer Dogfight game, that it is MSL (Mean Sea Level), not AGL (Above Ground Level). This means that if you start over a mountain, your AGL may be 1,000 feet while your MSL is 7,000 feet.
Tactical Engagement and Campaign: We recommend that all players choose either Taxi or Takeoff to start their mission for better synchronization of all aircraft. If any player in a flight chooses Taxi, all flight members will start by taxiing in multiplayer missions.
Multiple Connections: If you have a modem and are hooked up to a LAN, you may not be able to connect to another player. This is because Falcon 4.0 does not know which IP address to use, the one for your modem or the one for your LAN. If this is a problem, you need to run the HostIDX utility. Select "Run" from the Start menu and type "C:\MicroProse\Falcon4\HostIDX 1" to use your computer's second IP address. Type "HOSTIDX 0" to use your computer's original IP address.
Customer Support
If none of the information above or in the FAQ helps to solve your problem, please contact Customer Support.
We recommend running both F4INFO.EXE and MPRTEST.EXE and printing out the information displayed onscreen before calling Customer Support with a problem.
We would also appreciate having the following information:
